Motion-based communication mode selection

ABSTRACT

Embodiments of the invention are directed to apparatus and methods for providing motion-based communication mode selection on a mobile device. In some embodiments, a mobile device can compare a detected motion of the mobile device to a plurality of predetermined motions. Each of the plurality of predetermined motions being can be associated with a different communication mode of the mobile device. A communication mode associated with the detected motion can be identified by the mobile device based at least in part on the comparison, and the identified communication mode can correspond to a communication protocol. The mobile device can generate a data message in accordance with the communication protocol, and can provide this data message to a receiver device.

CROSS-REFERENCES TO RELATED APPLICATIONS

The present application is a non-provisional application of and claimspriority to U.S. Provisional Application No. 62/053,019, filed on Sep.19, 2014, the entire contents of which are herein incorporated byreference for all purposes.

BACKGROUND

The present disclosure relates generally to mobile device communication,and more particularly to motion-based communication mode selection on amobile device.

Mobile devices such as smart phones can be configured for communicationusing many different communication protocols including cellular, WiFi,near field communication (NFC), Bluetooth, two-dimensional barcodes(e.g., QR codes), and the like. To initiate communication in a desiredprotocol, however, a user must typically have to open an application ontheir mobile device specifically associated with the communicationprotocol.

For example, in the context of a contactless payment transaction at amerchant point of sale (POS) terminal, a user may have the option toinitiate a payment with their mobile device by communicating with thePOS terminal using an NFC or two-dimensional barcode protocol. To selectthe desired protocol, the user generally must first “unlock” theirmobile device and then open a specific payment application before thepayment is initiated. In some instances, upon opening the paymentapplication, the user may also need to navigate through a list ofavailable protocols to locate and select the protocol desired for makingthe payment. This may be cumbersome and time-consuming for users, andmay result in delays at the merchant and may discourage users frommaking use of certain contactless protocols available to them.

In another example, a user may wish to use their mobile device to send amessage to another user's mobile device. To do so, however, the usermust typically first open an application on their mobile deviceconfigured to transmit the message in the desired communicationprotocol. If the user wishes to send an SMS text message, as an example,they may first need to open an application programmed to transmit SMStext messages. But if the user desires to send an email message, aseparate email application may first need to be opened. As in thecontactless payment scenario, this process can be time-consuming,especially when the user's mobile device includes many installedapplications that must be navigated to locate and select the applicationassociated with the desired communication protocol.

Embodiments of the invention address these and other problems.

BRIEF SUMMARY

Embodiments of the invention are directed to apparatus and methods forproviding motion-based communication mode selection on a mobile device.

One embodiment of the invention is directed to a mobile the device. Themobile device can comprise a motion detection sensor, a communicationinterface, and a processor coupled to the motion detection sensor andthe communication interface. The processor can be configured to receivea signal from the motion detection sensor, the signal identifying amotion of the mobile device detected by the motion detection sensor. Theprocessor can be further configured to compare the detected motion ofthe mobile device to a plurality of predetermined motions, each of theplurality of predetermined motions being associated with a differentcommunication mode of the mobile device, and to identify a communicationmode associated with the detected motion of the mobile device based atleast on part on the comparison, the identified communication modecorresponding to a communication protocol. The processor can be furtherconfigured to generate a data message in accordance with thecommunication protocol, and provide the data message to a receiverdevice via the communication interface.

Another embodiment of the invention is directed to a method. The methodcan comprise detecting, by a mobile device, a motion of the mobiledevice. The mobile device can compare the detected motion of the mobiledevice to a plurality of predetermined motions, each of the plurality ofpredetermined motions being associated with a different communicationmode of the mobile device. The mobile device can identify acommunication mode associated with the detected motion of the mobiledevice based at least in part on the comparison, the identifiedcommunication mode corresponding to a communication protocol. The mobiledevice can generate a data message in accordance with the communicationprotocol, and provide the data message to a receiver device.

These and other embodiments of the invention are described in detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an exemplary mobile communicationsystem in accordance with some embodiments.

FIG. 2 illustrates a block diagram of an exemplary mobile device inaccordance with some embodiments.

FIG. 3 illustrates an exemplary data table containingmotion-to-communication mode mappings in accordance with someembodiments.

FIG. 4 illustrates a block diagram of an exemplary receiver device inaccordance with some embodiments.

FIG. 5 illustrates a block diagram of an exemplary mobile paymentprocessing system in accordance with some embodiments.

FIG. 6 illustrates a flowchart of an exemplary method of providingmotion-based communication mode selection on a mobile device inaccordance with some embodiments.

FIGS. 7A-7B illustrate an exemplary sequence for initiating an NFCcommunication mode on a mobile device in accordance with someembodiments.

FIGS. 8A-8B illustrate an exemplary sequence for initiating atwo-dimensional barcode communication mode on a mobile device inaccordance with some embodiments.

FIGS. 9A-9C illustrate an exemplary sequence for initiating a messagingcommunication mode on a mobile device in accordance with someembodiments.

FIG. 10 illustrates a block diagram of an exemplary computer apparatusin accordance with some embodiments.

DEFINITIONS

Prior to further describing embodiments of the invention, a descriptionof some terms may be helpful in understanding embodiments of theinvention.

A “mobile device” may include any computing device configured tocommunicate with another computing device, such as a receiver device. Amobile device may be in any suitable form. Exemplary mobile devicesinclude, but are not limited to, mobile phones (e.g., smart phones),tablet computers, media players, wearable devices (e.g., smart watches,fitness bands, ankle bracelets, rings, earrings, and the like), laptopcomputers, net books, PDAs, and the like. A mobile device may use anysuitable contact-based or contactless mode of operation to communicatewith a receiver device.

A “receiver device” may include any computing device configured tocommunicate with a mobile device. Exemplary receiver devices include,but are not limited to, merchant POS terminals, server computers,desktop computers, mobile phones (e.g., smart phones), tablet computers,media players, wearable devices (e.g., smart watches, fitness bands,ankle bracelets, rings, earrings, and the like), laptop computers, netbooks, PDAs, and the like. A receiver device may use any suitablecontact-based or contactless mode of operation to communicate with amobile device device.

A “communication interface” may include any component(s) of a mobiledevice configured to facilitate communication by the mobile device. Acommunication interface can include any suitable hardware and/orsoftware including, but not limited to, a display screen, NFC elements,WiFi (e.g., IEEE 802.11) elements, Bluetooth elements, and the like, orany suitable combination thereof.

A “processor” may include hardware within a mobile device that carriesout instructions embodied as code in a memory (e.g., a non-transitorycomputer-readable medium). An exemplary processor may be a centralprocessing unit (CPU). As used herein, a processor can include asingle-core processor, a plurality of single-core processors, amulti-core processor, a plurality of multi-core processors, or any othersuitable combination of hardware configured to perform arithmetical,logical, and/or input/output operations of a mobile device.

A “motion detection sensor” may include hardware and/or software withina mobile device configured to detect motion of the mobile device.Exemplary motion detection sensors include, but are not limited to,accelerometers, gyroscopes, compasses, altimeters, and the like.

A “motion” of a mobile device may include any movement of a mobiledevice from one position to another position, from one orientation toanother orientation, and/or the like. A motion of a mobile device caninclude, for example, a rotation of the mobile device, a translationalmotion of the mobile device, or a combination thereof. In someembodiments, a motion of a mobile device can include a particular pathtravelled by the mobile device from one position to another.

A “communication mode” may include any mode of a mobile device thatfacilitates communication by the mobile device with a receiver device. Acommunication mode can correspond to a communication protocol. Exemplarycommunication protocols can include, but are not limited to, cellular,WiFi, NFC, Bluetooth, two-dimensional barcode, and the like.

A “confidence value” may include a value (e.g., a number) representing alevel of confidence that a criteria is met. In some embodiments, aconfidence value calculated by a mobile device can represent thelikelihood a detected motion of the mobile device corresponds to apredetermined motion of the mobile device, the predetermined motionbeing associated with a communication mode of the mobile device.

“Location determination circuitry” can include hardware and/or softwarewithin a mobile device and configured to determine a location of themobile device. Location determination circuitry can utilize varioustypes of data including, but not limited to, Global Positioning System(GPS) data, cellular phone tower triangulation data, cellular phonetower signal strength data, wireless access point location data, anInternet Protocol (IP) address, or any other suitable data usable by thelocation determination circuitry to determine a location of a mobiledevice.

DETAILED DESCRIPTION

Embodiments of the invention are directed to apparatus and methods forproviding motion-based communication mode selection on a mobile device.A mobile device (e.g., a smart phone) can include a motion detectionsensor configured to detect motions (e.g., rotational and/ortranslation) of the mobile device. When such a motion is detected, themobile device can compare the detected motion to a plurality ofpredetermined motions (e.g., stored in a memory of the mobile device).Each of the predetermined motions can be associated with a differentcommunication mode of the mobile device configured, for example, tofacilitate communication by the mobile device using a particularprotocol (e.g., NFC, WiFi, two-dimensional barcode, Bluetooth, etc.).

The detected motion of the mobile device can be compared to theplurality of predetermined motions. In some embodiments, this comparisoncan include a calculation by the mobile device of a confidence valuecorresponding to a likelihood the detected motion corresponds to one ofthe plurality of predetermine motions. Based at least in part on thecomparison, the mobile device can identify a communication mode of themobile device associated with the detected motion, the communicationmode corresponding to a communication protocol. For example, in someembodiments, the mobile device can determine that the calculatedconfidence value exceeds some threshold confidence value. In response, adata message can be generated by the mobile device in accordance withthe communication protocol. This data message can then be transmitted bythe mobile device to a receiver device.

In some embodiments, the mobile device can also include locationdetermination (e.g., GPS) circuitry configured to determine a locationof the mobile device. In such embodiments, as described in furtherdetail below, the location of the mobile device at the time the motionis detected can be used to further identify and confirm thecommunication mode associated with the detected motion.

As an illustration, a user may initiate a contactless paymenttransaction at a merchant POS terminal using their mobile device. ThePOS terminal may be configured to accept payment via multiplecommunication protocols including, for example, NFC and two-dimensionalbarcode. In this illustration, the user's mobile device can include amemory storing a plurality of communication modes, with each mode beingassociated with a different predetermined motion of the mobile device.For example, the memory may associate an NFC communication mode with adownward translational motion of the mobile device, and may furtherassociate a two-dimensional barcode communication mode with a rotationalmotion of the mobile device.

The user can select a desired communication mode for initiating thepayment transaction by moving the mobile device in one of thepredetermined manners. For example, if the user wishes to use NFC toconduct the payment transaction, they can move the mobile device in adownward translational motion (e.g., towards an NFC receiver of the POSterminal). Alternatively, if the user prefers a two-dimensional barcodetransaction, the user can cause the mobile device to rotate such that adisplay screen of the mobile device is facing an optical barcode scannerof the POS terminal at the end of the rotation. In either case, a motiondetection sensor (e.g., an accelerometer, gyroscope, and/or the like)can detect the motion of the mobile device caused by the user.

Upon detecting the motion, the mobile device can then compare thedetected motion to the plurality of predetermined motions stored in thememory of the mobile device. This comparison can involve the mobiledevice calculating a confidence value representing the likelihood thatthe detected motion of the mobile device corresponds to one of theplurality of predetermined motions. In some embodiments, such aconfidence value can also be affected by a location of the mobiledevice. For example, using location determination circuitry, the mobiledevice can determine that it is currently located at a merchant. Sincethe user may initiate a motion of the mobile device in a scenario wherea contactless payment is not desired (e.g., at the user's home),determining the location of the mobile device can prevent falsepositives. In some embodiments, the calculated confidence value can bedecreased or increased based on the determined location of the mobiledevice. In this illustration, the determination that the mobile deviceis located at a merchant may increase the confidence value.

If the calculated confidence value meets (or exceeds) a thresholdconfidence value, this may confirm to the mobile device that thedetected motion corresponds to one of the plurality of predeterminedmotions stored in the memory of the mobile device. A communication modecan then be identified by the mobile device, the communication modebeing associated with the detected motion. In this illustration, if thedetected motion is the downward translational motion, the identifiedmode can be the NFC communication mode. If, however, the detected motionis the rotational motion, the identified communication mode can insteadbe the two-dimensional barcode mode.

In response to identifying the associated mode and correspondingcommunication protocol, the mobile device can generate a data message inaccordance with the protocol. This data message can then be provided tothe merchant's mobile POS terminal to initiate the contactless paymenttransaction. For example, if the NFC communication mode was identified,the mobile device can generate and transmit an NFC (e.g., radio)communication message to the NFC receiver of the POS terminal, therebyinitiating the contactless transaction. Alternatively, if thetwo-dimensional barcode mode was identified, the mobile device cangenerate and display a two-dimensional barcode on the display screen ofthe mobile device. An optical barcode scanner of the POS terminal canread the displayed two-dimensional barcode to initiate the paymenttransaction.

Embodiments of the invention can provide a number of advantages. Forexample, by utilizing motion-based communication mode selection, a usercan initiate one of many communication modes of their mobile devicewithout having to unlock the mobile device, open a specific application,and navigate through a list of available communication protocols tolocate and select the desired protocol. This may result in communicationmode selection being more convenient and efficient for users, whileencouraging users to make use of the many potential communicationprotocols available to them.

In some embodiments, a user may still be required to open an application(e.g., a payment application) prior to selecting a particularcommunication mode. Even in such embodiments, however, the user may notneed to navigate through and select the desired protocol. This isbecause the user can simply move their mobile device in a predeterminedmanner associated with the protocol to be utilized. Upon confirming at athreshold level of confidence that a detected motion is associated witha communication mode, the mobile device can communicate with a receiverdevice using the corresponding protocol without further input from theuser. Moreover, irrespective of whether an application is first openedby the user, embodiments can provide a solution to existing scenarioswhere different communication modes require that the user open differentapplications corresponding to each mode (e.g., an email application, SMStext message application, etc.).

I. Exemplary Systems

FIG. 1 illustrates a block diagram of an exemplary mobile communicationsystem 100 in accordance with some embodiments. As seen in FIG. 1,system 100 can include a mobile device 102 and a receiver device 104.Mobile device 102 can communicate with receiver device 104 using aplurality of different communication modes, each being associated with aparticular communication protocol. For example, mobile device 102 andreceiver device 104 can be configured to exchange data messages 106′ and106″ using many different communication protocols.

Mobile device 102 can be in any suitable form. For example, a suitablemobile device can be hand-held and compact so that it can fit into awallet and/or pocket (e.g., pocket-sized) of a user. Exemplary mobiledevices can include, but are not limited to, mobile phones (e.g., smartphones), tablet computers, media players, wearable devices (e.g., smartwatches, fitness bands, ankle bracelets, rings, earrings, and the like),laptop computers, net books, PDAs, and the like. Mobile device 102 canoperate in a contact-based mode (e.g., using data stored in a magneticstripe format) and/or in a contactless mode (e.g., using atwo-dimensional barcodes displayed on a display screen, NFC, WiFi,Bluetooth, the like) to communicate with receiver device 104.

Receiver device 104 can also be in any suitable form. Exemplary receiverdevices can include, but are not limited to, merchant POS terminals,server computers, desktop computers, mobile phones (e.g., smart phones),tablet computers, media players, wearable devices (e.g., smart watches,fitness bands, ankle bracelets, rings, earrings, and the like), laptopcomputers, net books, PDAs, and the like. Receiver device 104 mayoperate in any suitable contact-based or contactless mode to communicatewith mobile device 102.

FIG. 2 illustrates a block diagram of an exemplary mobile device, i.e.mobile device 102, in accordance with some embodiments. As shown, mobiledevice 102 can comprise a plurality of hardware components and softwaremodules 102(a)-102(o). However, it should be appreciated that this isprovided for illustration purposes only, and each of the components,modules, and associated functionality described herein may be provided(or otherwise performed) by the same or different components and/ormodules. That is, mobile device 102 may, for example, perform some ofthe relevant functions and steps described herein through the use of anysuitable combination of software instructions and/or hardwareconfigurations. It should also be noted that although FIG. 2 illustratesall of the components and modules located on a single device (i.e.mobile device 102), the disclosure is not meant to be so limited.Moreover, a system for implementing the functionality described hereinmay have additional components and/or modules or less than all of thesecomponents and modules. Additionally, some components and/or modules maybe located on other devices such as a remote server or other localdevices that are functionally connected to mobile device 102.

Mobile device 102 is shown as comprising a processor 102(a) and a memory102(i) operatively coupled to processor 102(a). Processor 102(a) cancarry out instructions embodied as code in memory 102(i). Processor102(a) can be a central processing unit (CPU). Exemplary processorsinclude, but are not limited to, a single-core processor, a plurality ofsingle-core processors, a multi-core processor, a plurality ofmulti-core processors, or any other suitable combination of hardwareconfigured to perform arithmetical, logical, and/or input/outputoperations of mobile device 102. Memory 102(i) can be a non-transitorycomputer readable medium comprising any suitable combination of volatileand/or non-volatile memory such as, for example, buffer memory, RAM,DRAM, ROM, flash, disk drives, or any other suitable storage media. Insome embodiments, one or more of the software modules illustrated inFIG. 2 can be stored on memory 102(i) including, for example, a mobileapplication 102(j) and motion-to-communication mode mappings 102(k).

Mobile application 102(i) can be any suitable application executable byprocessor 102(a) of mobile device 102. In some embodiments, mobileapplication 102(i) is a mobile payment application. In some otherembodiments, mobile application 102(i) can instead be a more genericapplication programmed to facilitate the motion-based communication modeselection techniques described herein.

Mobile device 102 can further include one or more motion detectionsensors 102(g) operatively coupled to processor 102(a). Motion detectionsensors 102(g) can comprise hardware and/or software configured todetect various motions of mobile device 102. Exemplary motion detectionsensors can include, but are not limited to accelerometers, gyroscopes,compasses, altimeters, and the like. Motion detection sensors 102(g) candetect a movement of mobile device 102 from one position to anotherposition, from one orientation to another orientation, and/orcombinations thereof. Suitable detectable motions can include, but arenot limited to, rotations, translational motions, and combinationsthereof. In some embodiments, detectable motions can include particularpaths traveled by mobile device 102 from one position to another.

In some embodiments, mobile device 102 can further include locationdetermination circuitry 102(h) operatively coupled to processor 102(a)and configured to determine a location (e.g., geographic location) ofmobile device 102. Location determination circuitry 102(h) can includeany suitable hardware and/or software, and can utilize various types ofdata to determine a location of mobile device 102. Suitable data usableby location determination circuitry 102(h) can include, but is notlimited to, GPS data, cellular phone tower triangulation data, cellularphone tower signal strength data, wireless access point location data,an Internet Protocol (IP) address, and the like.

Mobile device 102 can further include a communication interface 102(b)operatively coupled to processor 102(a). Communication interface 102(b)can include any suitable combination of components configured tofacilitate communication by mobile device 102. For example, as shown inFIG. 2, communication interface 102(b) can include a display screen102(c), contactless elements 102(d), WiFi elements 102(e), and Bluetoothelements 102(f).

Display screen 102(c) can be configured to communicate displayed content(e.g., a two-dimensional barcode) to another device (e.g., receiverdevice 104) and, in some embodiments, can be a touch screen furtherconfigured to receive touch input from a user. Contactless elements102(d) can be configured to communicate using a short range wirelesscommunication protocol such as NFC. Contactless elements 102(d) caninclude a semiconductor chip (or other data storage element) with anassociated wireless transfer (e.g., data transmission) element, such asan antenna. WiFi elements 102(e) can include any hardware and/orsoftware configured to communicate using a local area wireless computernetworking protocol (e.g., an IEEE 802.11 standard). Bluetooth elements102(f) can include any suitable hardware and/or software configured tocommunicate using ultra high frequency (UHF) radio waves.

As shown in FIG. 2, mobile device 102 can further include an antenna102(1) which can be configured, for example, to communicate via acellular network (e.g., 3G, 4G EDGE, and the like), input elements102(m) such as one or more buttons which can be configured to allow auser to provide input to mobile device 102, a speaker 102(n) configuredto provide audio output, and a microphone 102(o) configured to receiveaudio input. A housing (not shown) may house one or more of the hardwarecomponents illustrated in FIG. 2.

FIG. 3 illustrates an exemplary data table 300 containingmotion-to-communication mode mappings 102(i) in accordance with someembodiments. As described above and shown in FIG. 3,motion-to-communication mode mappings 102(i) can be stored in memory102(i) of mobile device 102. In some other embodiments, all or part ofmotion-to-communication mode mappings 102(i) can be stored remotely frommobile device 102 in, for example, a remote server computercommunicatively coupled to mobile device 102.

As shown in FIG. 3, data table 300 can include relational data fieldscontaining data representing predetermined motions 300(a) of mobiledevice 102, associated communication modes 300(b), and correspondingconfidence threshold values 300(c). Motions 300(a) can include rotationsof mobile device 102, translational motions of mobile device 102, andcombinations thereof. Rotations can be with respect to any suitablenumber of axes. For example, in some embodiments, rotations can includerotations about an x-axis running parallel to the length of mobiledevice 102, rotations about a y-axis running parallel to the width ofmobile device 102 (and perpendicular to the x-axis), and rotations abouta z-axis running parallel to the thickness of mobile device 102 (e.g.,intersecting display screen 102(c) and perpendicular to both the x-axisand y-axis). Any suitable translational motions of mobile device 102 canalso be represented in data table 300. Such translational motions can bein any suitable direction, across any suitable distance, and inaccordance with any suitable path.

Communication modes 100(b) in data table 300(b) are each associated withone of motions 300(a) of mobile device 102. This, however, is notintended to be limiting. In some embodiments, a communication mode maybe associated with more than one motion of mobile device 102 such thatthe communication mode can be initiated in response to multipledifferent motions of mobile device 102. Each of communication modes300(b) of mobile device 102 can be associated with a communicationprotocol. As described herein, exemplary communication protocols caninclude, but are not limited to, cellular, WiFi, NFC, Bluetooth,two-dimensional barcode, and the like.

In some embodiments, motions 300(a) and associated communication modes300(b) can be established automatically as default settings.Alternatively, in some embodiments, communication modes 300(b) andassociated motions 300(a) can be provided by the user. For example, in asetup process, the user can select a particular communication mode andthen move mobile device 102 in a desired way, thereby resulting in theuser-provided motion being stored in data table 300 and associated withthe selected communication mode.

Confidence threshold values 300(c) can include values (e.g., numbers)representing a minimum confidence level that must be calculated bymobile device 102 in order to initiate a communication mode in responseto detecting an associated motion of mobile device 102. In someembodiments, confidence threshold values 300(c) can be default valuesestablished for each motion and associated communication mode.Confidence threshold values 300(c) can be configured or otherwisecustomized by a user in some embodiments. Confidence threshold values300(c) can be a different value for each motion and associatedcommunication mode or, in some embodiments, some or all of the possibleassociated motions and communication modes can have the same confidencethreshold value. Confidence threshold values 300(c) can be setautomatically or by the user to avoid false positives where aninadvertent motion of mobile device 102 (or a motion intended by theuser for other purposes) causes mobile device 102 to initiate acommunication mode. For example, when a motion is similar to a commonmotion regularly used (e.g., lifting the mobile device up to the user'sear), a confidence threshold value associated with a similarpredetermined motion can be set as a high value. As another example, forhighly specific and uncommon motions (e.g., involving combinations ofrotations and translational motions), the associated confidencethreshold value can be lower since there is less likelihood of a falsepositive.

Predetermined motions 300(a) can include motion data that can becompared to motions detected by mobile device 102. For example,rotational motions can be represented by motion data describing one ormore axes of rotation, degrees of rotation (e.g., 45°, 90°, 135°, 180°,etc.), and other measurable aspects of a rotation of mobile device 102.Translational motions can be represented by motion data describingcoordinates (e.g., in a reference coordinate system) corresponding tomovements of mobile device 102 from one position to another. Suchtranslational motions can be linear or curved. Thus, in someembodiments, the particular paths of translational movement of mobiledevice 102 can be represented by motion data in data table 300. When amotion of mobile device 102 is detected, predetermined motions 300(a)can be compared to the detected motion. If a match if found with aconfidence level equal to or greater than the corresponding confidencethreshold value included in data table 300, the associated communicationmode can be initiated (e.g., by generating and transmitting a datamessage in accordance with a protocol corresponding to the communicationmode).

It should be noted that the arrangement and content of fields shown indata table 300 are provided only as an illustration. Data tablesaccording to embodiments of the invention may include any suitablenumber of fields including fewer or more fields than that shown in datatable 300 and/or different data fields altogether. For example, in someembodiments, data table 300 can include data describing likely (and/orunlikely) locations at which a user may wish to initiate a particularcommunication mode. In the context of communication modes used toconduct electronic payment transactions, likely locations may includemerchant locations. In some embodiments, when a detected motion is“matched” to a predetermined motion at a location (or type of location)included in data table 300, this may result in an increased confidencevalue calculated by mobile device 102. Alternatively, if the motion isdetected at a location at which a user is unlikely to desire theassociated communication mode (e.g., a contactless payment mode when theuser is at their home), this may reduce the calculated confidence value.Embodiments of the invention may also include other arrangements of datadifferent than the relational data fields illustrated in FIG. 3.

FIG. 4 illustrates a block diagram of exemplary receiver device 104 inaccordance with some embodiments. As shown, receiver device 104 cancomprise a plurality of hardware components and software modules104(a)-104(k). However, it should be appreciated that this is providedfor illustration purposes only, and each of the components, modules, andassociated functionality described herein may be provided (or otherwiseperformed) by the same or different components and/or modules. That is,receiver device 104 may, for example, perform some of the relevantfunctions and steps described herein through the use of any suitablecombination of software instructions and/or hardware configurations. Itshould also be noted that although FIG. 4 illustrates all of thecomponents and modules located on a single device (i.e. receiver device104), the disclosure is not meant to be so limited. Moreover, a systemfor implementing the functionality described herein may have additionalcomponents and/or modules or less than all of these components andmodules. Additionally, some components and/or modules may be located onother devices such as a remote server or other local devices that arefunctionally connected to receiver device 104.

Receiver device 104 is shown as comprising a processor 104(a) and amemory 104(b) operatively coupled to processor 104(a). Processor 104(a)can carry out instructions embodied as code in memory 104(b). Processor104(a) can be a central processing unit (CPU). Exemplary processorsinclude, but are not limited to, a single-core processor, a plurality ofsingle-core processors, a multi-core processor, a plurality ofmulti-core processors, or any other suitable combination of hardwareconfigured to perform arithmetical, logical, and/or input/outputoperations of receiver device 104. Memory 104(b) can be a non-transitorycomputer readable medium comprising any suitable combination of volatileand/or non-volatile memory such as, for example, buffer memory, RAM,DRAM, ROM, flash, disk drives, or any other suitable storage media. Insome embodiments, one or more of the software modules illustrated inFIG. 4 can be stored on memory 104(b).

Receiver device 104 can further include a communication interface 104(f)operatively coupled to processor 104(a). Communication interface 104(f)can include any suitable combination of components configured tofacilitate communication by receiver device 104 with, for example, amobile device (e.g., mobile device 102) or other device (e.g., anothermobile device, a remote server computer, etc.). For example, as shown inFIG. 4, communication interface 104(f) can include a card reader 104(g),an optical scanner 104(h), contactless elements 104(i), WiFi elements104(j), and Bluetooth elements 104(k).

Card reader 104(g) can be configured receive magnetic stripe data from apayment device such as mobile device 102 and/or from a magnetic stripeon a conventional payment card (e.g., a credit card, debit card, prepaidcard, or the like).

Optical scanner 104(h) can include hardware and software configured tofacilitate communication by optical means. In some embodiments, suchoptical means can include communication by way of two-dimensionalbarcodes generated by a mobile device (e.g., mobile device 102). Forexample, in some embodiments, optical scanner 104(h) can include a lightsource, a lens, and light sensor that translates optical impulses intoelectrical impulses. Optical scanner 104(h) can further include decodercircuitry configured to analyze a two-dimensional barcode detected bythe light sensor in order to decode the data represented by the barcode.

Contactless elements 104(i) can be configured to communicate using ashort range wireless communication protocol such as NFC. Contactlesselements 104(i) can include a semiconductor chip (or other data storageelement) with an associated wireless transfer (e.g., data receiving)element, such as an antenna. WiFi elements 104(j) can include anyhardware and/or software configured to communicate using a local areawireless computer networking protocol (e.g., an IEEE 802.11 standard).Bluetooth elements 104(k) can include any suitable hardware and/orsoftware configured to communicate using ultra high frequency (UHF)radio waves.

As shown in FIG. 4, receiver device 104 can further include a messagingmodule 104(c), a network interface 104(d), and an output device 104(e).A housing (not shown) may house one or more of the componentsillustrated in FIG. 4.

Output device 104(e) may be configured or programmed to perform some orall of the functionality associated with providing output to a user.Output device 104(e) may include a display and/or an audio output devicesuch as one or more speakers. In some embodiments, output device 104(e)can also include one or more buttons or other input elements to allowinput to be provided to receiver device 104 by a user. In someembodiments, output device 104(e) can include a touchscreen that mayoperate to both receive input and provide visual output.

Messaging module 104(c) may be configured to perform some or all thefunctionality associated with exchanging and analyzing data messages. Insome embodiments, where receiver device 104 is a merchant POS terminal,messaging module 104(c) can be configured to facilitate the exchange andanalysis of authorization messages. For example, messaging module 104(c)can generate an authorization request message for an electronic paymenttransaction, receive an authorization response message for thetransaction (e.g., from an account issuer computer via a paymentprocessing network), and can provide an indication of the authorizationdecision using output device 104(e). Such authorization messages can betransmitted and received by receiver device 104 using, for example,network interface 104(d). In some embodiments, network interface 104(d)can be configured to exchange data messages with a payment processingnetwork, acquirer computer, issuer computer, gateway computer, processorcomputer, or other computing device using any suitable communicationprotocol (e.g., ISO 8583).

In some embodiments, as described herein, motion-based communicationmode selection can be performed in the context of an electronic paymenttransaction. FIG. 5 illustrates a block diagram of an exemplary mobilepayment processing system 500 in accordance with some embodiments.

System 500 may include one or more users, mobile devices, receiverdevices, acquirer computers, networks, and issuers computers. Forexample, as illustrated in FIG. 5, system 500 can include a user 502having a mobile device 504 (e.g., corresponding to mobile device 102shown in FIG. 1 and described above). User 502 can be an individual, anorganization such as a business, or any other suitable entity capable ofpurchasing goods and/or services using mobile device 504.

Mobile device 504 can be in any suitable form as described above withrespect to mobile device 102. System 500 can further include receiverdevice 506 such as a mobile POS terminal which may be operated by amerchant. As used herein, a “merchant” may refer to an entity thatengages in transactions and that can sell goods and/or services toconsumers. Receiver device 506 can be in any suitable form as describedabove with respect to receiver device 104. Receiver device 106 may alsobe in any suitable form. Receiver device 506 can include externalcommunication interfaces (e.g., communication interface 104(f) andnetwork interface 104(d)) for communicating with payment devices (e.g.,mobile device 504) and other entities in system 500, system memory(e.g., memory 104(b)), and a data processor (e.g., processor 104(a)) forfacilitating the exchange of electronic data messages.

System 500 may further include an acquirer computer 508 operated by anacquirer. As used herein, an “acquirer” may refer to a business entity(e.g., a commercial bank or financial institution) that has a businessrelationship with a particular merchant or similar entity, and thatfacilitates clearing, settlement, and any other suitable aspect ofelectronic payment transactions. Acquirer computer 507 may include anexternal communication interface (e.g., for communicating with receiverdevice 506, a payment processing network 510, or other entity), systemmemory comprising one or more modules to generate and utilize electronicmessages, and a data processor for facilitating the exchange ofelectronic data messages.

System 500 may further include an issuer computer 512 operated by anissuer. As used herein, an “issuer” may refer to a business entity(e.g., a bank or other financial institution) that maintains financialaccounts for consumers and that may issue payment accounts and consumerpayment devices (e.g., credit cards, debit cards, and the like) used toaccess funds of such accounts. Some entities may perform both issuer andacquirer functions. Issuer computer 512 may include an externalcommunication interface (e.g., for communicating with payment processingnetwork 510 or other entity), system memory comprising one or moremodules to generate and utilize electronic messages, and a dataprocessor for facilitating the exchange of electronic data messages.

Payment processing network 510 may be included in system 500, and caninclude data processing subsystems, networks, and operations used tosupport and deliver authorization services, exception file services, andclearing and settlement services. For example, payment processingnetwork 510 may comprise a server computer, coupled to a networkinterface (e.g. by an external communication interface), and adatabase(s) of information. An exemplary payment processing network mayinclude VisaNet™. Payment processing networks such as VisaNet™ are ableto process credit card transactions, debit card transactions, and othertypes of commercial transactions. VisaNet™, in particular, includes aVIP system (Visa Integrated Payments system) which processesauthorization requests and a Base II system which performs clearing andsettlement services. Payment processing network 510 may include anexternal communication interface (e.g., for communicating with acquirercomputer 508, issuer computer 512, or other entity in system 500),system memory comprising one or more modules to generate and utilizeelectronic messages, and a data processor for facilitating the exchangeof electronic data messages.

In some embodiments, to conduct an electronic payment transaction, user502 may cause mobile device 504 to interact with receiver device 506 inaccordance with the motion-based communication mode techniques describedherein. Account information associated with a payment account of user502 can then be received at receiver device 506 and transmitted toissuer computer 512 via acquirer computer 508 and payment processingnetwork 510.

Receiver device 506, acquirer computer 508, payment processing network510, and issuer computer 512 may be in operative communication with eachother. For example, as described above, some or all of these componentsof system 500 can include an external communication interface. As usedherein, an “external communication interface” may refer to any hardwareand/or software that enables data to be transferred between two or morecomponents/entities of system 500 (e.g., between devices residing atlocations such as at an issuer, acquirer, merchant, payment processingnetwork, etc.). Some examples of external communication interfaces mayinclude a modem, a network interface (such as an Ethernet card), acommunications port, a Personal Computer Memory Card InternationalAssociation (PCMCIA) slot and card, and the like. Data transferred viaan external communications interface may be in the form of signals whichmay be electrical, electromagnetic, optical, or any other signal capableof being received by the external communications interface. Theseelectronic data messages that may comprise data or instructions may beprovided between one or more of the external communications interfacevia a communications path or channel. As noted above, any suitablecommunication path or channel may be used such as, for instance, a wireor cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link, a WAN or LAN network, the Internet, or any othersuitable method.

As would be understood by one of ordinary skill in the art, any suitablecommunications protocol for storing, representing, and transmitting databetween components/entities of system 500 may be used. Some examples ofsuch methods may include utilizing predefined and static fields (such asin core TCP/IP protocols); “Field: Value” pairs (e.g., HTTP, FTP, SMTP,POP3, and SIP); an XML based format; and/or Tag-Length-Value format.

In some embodiments, mobile device 504 payment device 104 can facilitatean “electronic” or “digital wallet” that may be used to conduct anelectronic payment transaction. In such embodiments, an electronicwallet server 516 may be in operational communication with mobile device504, payment processing network 510, and/or other entity in system 500.For example, electronic wallet server 516 may communicate with mobiledevice 514 across a network 520 (e.g., the Internet) and using aninternet protocol gateway (IPG) 514. Electronic wallet server 516 maymaintain an association between the user's digital wallet and one ormore payment accounts (e.g., credit, debit, prepaid accounts, and thelike) in an electronic wallet database 518. Electronic wallet server 516can provide a web interface (e.g. through one or more web pages) toreceive and transmit requests for payment services and/or may provide anapplication program interface (API) on mobile device 504 to provide theweb service.

Many of the data processing functions and features of some embodimentsof the invention may be present in mobile device 504. It should beunderstood, however, that such functions and features could be presentin other components/entities of system 500 in some embodiments.

A description of a typical electronic transaction flow using system 500may be helpful in understanding embodiments of the invention. As aninitial step, user 502 can attempt to purchase goods and/or servicesfrom a merchant. In embodiments of the invention, this can involve amotion-based transaction mode selection technique where user 502 causesmobile device 504 to move in a predetermined manner to select thedesired communication mode and protocol for initiating the electronicpayment transaction. Upon mapping the detected motion to a particularcommunication mode, mobile device 504 can generate and provide a datamessage including payment account information to receiver device 506.

Receiver device 506 can then generate an authorization request messagefor the transaction including information such as the transactionamount, information about the user's payment account, etc., and cantransmit this data message to acquirer computer 508. The authorizationrequest message can then be transmitted by acquirer computer 508 topayment processing network 510 which may forward the message to issuercomputer 512 operated by the issuer of the user's payment account.

Upon receipt of the authorization request message, issuer computer 512can perform a number of processes (e.g., verifying the account,confirming that the account has a sufficient balance or available creditto cover the amount of the transaction, consumer fraud detection, and/orother processes) to determine whether to authorize the transaction.After making an authorization decision, an authorization responsemessage is generated by issuer computer 512 including an indication ofthe authorization decision. The authorization response message istransmitted by issuer computer 512 to payment processing network 510,from payment processing network 510 to acquirer computer 508, and thenfrom acquirer computer 508 to receiver device 506. An indication maythen be provided by receiver device 506 whether authorization of thetransaction has been approved or declined by the issuer. In someembodiments, this may involve displaying an indication of theauthorization decision on a display of receiver device 506.

At the end of the day, if the transaction was authorized, a clearing andsettlement process can be conducted by payment processing network 510,acquirer computer 508, and issuer computer 512. A clearing process mayinclude the exchange of financial details between acquirer computer 508and issuer computer 512 across payment processing network 510 tofacilitate posting to the user's account and reconciliation of thesettlement position. A settlement process may include the actualtransfer of funds from the issuer to the acquirer. In some embodiments,to initiate settlement, acquirer computer 508 can transmit a settlementfile including an approval code for the transaction (along with otherapproved transactions in a batch format) to payment processing network510 which can then communicate with issuer computer 512 and the acquirercomputer 508 to facilitate the transfer of funds to an accountassociated with the merchant operating receiver device 506.

II. Exemplary Methods

FIG. 6 illustrates a flowchart of an exemplary method 600 of providingmotion-based communication mode selection on a mobile device inaccordance with some embodiments. The steps of method 600 may beperformed, for example, by a mobile device (e.g., mobile device 102,504, etc.). In other embodiments, one or more steps of method 400 may beperformed by another computing device such as a remote server computeror cloud-based device in communication with the mobile device.

In method 600, at step 602, a motion of the mobile device is detected bythe mobile device. In some embodiments, the motion of the mobile deviceis detected by a motion detection sensor of the mobile device that caninclude one or more of an accelerometer, a gyroscope, a compass, and analtimeter. The detected motion of the mobile device can include arotation of the mobile device, a translational motion of the mobiledevice, or a combination thereof.

At step 604, the mobile device can compare the detected motion of themobile device to a plurality of predetermined motions, each of theplurality of predetermined motions being associated with a differentcommunication mode of the mobile device. In some embodiments, theplurality of predetermined motions associated with the differentcommunication modes are stored in a memory of the mobile device.Comparing the detected motion of the mobile device to the plurality ofpredetermined motions, in some embodiments, can include the mobiledevice calculating a confidence value that the detected motion of themobile device corresponds to one of the plurality of predeterminedmotions, and the mobile device comparing the calculated confidence valueto a threshold confidence value.

At step 606, the mobile device can identify a communication modeassociated with the detected motion of the mobile device based at leastin part on the comparison, the identified communication modecorresponding to a communication protocol. Suitable communicationprotocols can include, but are not limited to, cellular, WiFi, NFC,Bluetooth, two-dimensional barcode, and the like. In some embodiments,identifying the communication mode associated with the detected motionof the mobile device can include the mobile device determining that thecalculated confidence value is equal to or greater than the thresholdconfidence value.

In some embodiments, at step 606 (or step 604), the mobile device candetermine a location of the mobile device. The location can bedetermined using location determination circuitry in the mobile devicethat receives and/or analyzes data such as GPS data, cellular phonetower triangulation data, cellular phone tower signal strength data,wireless access point location data, an Internet Protocol (IP) address,or the like, or combinations thereof. The location of the mobile devicemay affect the confidence value calculated by the mobile device sincethe location may provide an indication as to whether the motion of themobile device is intended by the user to initiate an associatedcommunication mode. When the location of the mobile device isdetermined, the communication mode associated with the detected motioncan be identified by the mobile device based in part on the determinedlocation and in part on the comparison at step 604.

At step 608, the mobile device can generate a data message in accordancewith the communication protocol corresponding to the identifiedcommunication mode. And, at step 610, the data message can be providedby the mobile device to a receiver device. In some embodiments,providing the data message to the receiver device can include the mobiledevice wirelessly transmitting the data message to the receiver device.In some embodiments, providing the data message to the receiver devicecan include the mobile device displaying the data message on a displayscreen of the mobile device. In such embodiments, the receiver devicemay have hardware (e.g., an optical scanner) configured to read the datamessage from the display screen of the mobile device.

FIGS. 7A-9C provide various illustrations of motion-based communicationmode selection in accordance with method 600. The illustrations depictedin FIGS. 7A-9C correspond to a mobile device identifying and initiatingdifferent communication modes of the mobile device in response todifferent predetermined motions, and in different operational contextsincluding electronic payment transactions and messaging applications.

In FIGS. 7A-7B, an exemplary sequence 700 for initiating an NFCcommunication mode on a mobile device in accordance with someembodiments is illustrated. As shown in FIG. 7A, a user 702 can be inpossession of a mobile device 704 including contactless elements 704(a).User 702 is in proximity to a receiver device 706 including contactlesselements 706(a). In sequence 700, receiver device 706 can be a merchantPOS terminal and user 702 may wish to conduct an electronic paymenttransaction using mobile device 704 in accordance with an NFC protocol.A memory of mobile device 704 may store a data table that associates apredetermined downward motion of mobile device 704 with an NFCcommunication mode of mobile device 704. As shown in FIG. 7A, user 702can initiate a downward motion 708 of mobile device 704 corresponding tothe downward motion stored in the memory.

A motion detection sensor (e.g., an accelerometer) in mobile device 704can detect motion 708 and transmit a signal identifying the motion to aprocessor of mobile device 704. The processor can then compare detectedmotion 708 to a plurality of predetermined motions (including thedownward motion) stored in the memory. For example, mobile device 704can determine that detected motion 708 is substantially similar to thestored downward motion. Using the processor, mobile device 704 cancalculate a confidence value that detected motion 708 corresponds to thestored downward motion based on, for example, similarities between therelative starting and ending position of mobile device 704, the path oftravel, and/or other factors.

As shown in FIG. 7B, the downward motion 708 may result in mobile device704 (and contactless elements 704(a)) being in proximity to contactlesselements 706(a) of receiver device 706. Upon identifying the NFCcommunication mode in response to detecting motion 708, comparing it tomotions stored in the memory, and determining that the calculatedconfidence value meets (or exceeds) a threshold value corresponding tothe detected motion 708 and associated NFC communication mode, mobiledevice 704 can then initiate the NFC communication mode. In FIG. 7B,this can involve contactless elements 704(a) of mobile device 704transmitting an NFC message 710 (e.g., including payment data) tocontactless elements 706(a) of receiver device 706, thereby initiatingthe electronic payment transaction in accordance with the NFC protocoldesired by user 702. In some embodiments, receiver device 706 can thenuse the received data to generate an authorization request message inaccordance with the electronic transaction processing flow describedabove with respect to FIG. 5.

FIGS. 8A-8B illustrate an exemplary sequence 800 for initiating atwo-dimensional barcode communication mode on a mobile device inaccordance with some embodiments. Sequence 800 illustrated in FIGS.8A-8B includes the same user 702, mobile device 704, and receiver device706 depicted in sequence 700. In this illustration, however, user 702can conduct an electronic payment transaction in accordance with atwo-dimensional barcode protocol instead of the NFC protocol depicted insequence 700 of FIGS. 7A-7B.

As shown in FIG. 8A, mobile device 704 can include a display screen704(b), and receiver device 706 can include an optical scanner 706(b)configured to read two-dimensional barcodes. As further shown in FIG.8A, prior to user initiating a motion of mobile device 704, a back face704(c) (e.g., opposite display screen 704(b)) may be facing receiverdevice 706. The data table stored in the memory of mobile device 704 mayassociate a rotational motion of mobile device 704 with atwo-dimensional barcode communication mode of mobile device 704. Asshown in FIG. 7A, user 702 can initiate a rotation 802 of mobile device704 corresponding to the rotation stored in the memory.

A motion detection sensor (e.g., a gyroscope) in mobile device 704 candetect rotation 802 motion and transmit a signal identifying the motionto the processor of mobile device 704. The processor can then comparethe detected rotation 802 to a plurality of predetermined motions(including the rotational motion) stored in the memory. For example,mobile device 704 can determine that detected rotation 802 issubstantially similar to the stored rotational motion. Using theprocessor, mobile device 704 can calculate a confidence value thatdetected rotation 802 corresponds to the stored rotational motion basedon, for example, similarities between the axis of rotations, degree ofrotation (e.g., 180°), and/or other factors.

In some embodiments, a rotation of mobile device 704 such as detectedrotation 802 may be a common motion used in other contexts unrelated toelectronic payment transactions. Thus, even if detected rotation 704accurately matches the predetermined motion stored in the memory, theuser may not have intended for detected motion 802 to initiate thetwo-dimensional barcode communication mode. In some embodiments, mobiledevice 704 can also include location determination circuitry (notshown). In sequence 800, mobile device 704 can determine its currentlocation including such circuitry, the location in this illustrationbeing at a merchant. In some embodiments, this determination can be madeby comparing the geo-coordinates (or street address) of mobile device704 with a database of mappings between merchants and geo-coordinates orstreet addresses, the database being stored in the memory of mobiledevice 704 or accessible from a remote server computer. Using such adatabase, the presence of mobile device 704 at the merchant can beconfirmed. This may also increase the confidence value calculated by theprocessor of mobile device 704.

As shown in FIG. 8B, rotation 802 may result in display 704(b) facingoptical scanner 706(b) of receiver device 706. Upon identifying thetwo-dimensional barcode communication mode in response to detectingrotation 802, comparing it to motions stored in the memory, determiningthe current location of mobile device 704, and determining that thecalculated confidence value meets (or exceeds) a threshold value, mobiledevice 704 can then initiate the two-dimensional barcode communicationmode. In FIG. 8B, this can involve processor of mobile device 704generating a two-dimensional barcode 804 (e.g., including encodedpayment data), and displaying barcode 804 on display screen 704(b).Optical scanner 706(b) of receiver device 706 can then optically receiveand decode the data contained in barcode 804, thereby initiating theelectronic transaction in accordance with the two-dimensional barcodeprotocol desired by user 702. In some embodiments, receiver device 706can then use the received data to generate an authorization requestmessage in accordance with the electronic transaction processing flowdescribed above with respect to FIG. 5.

FIGS. 9A-9C illustrate an exemplary sequence 900 for initiating amessaging communication mode on a mobile device in accordance with someembodiments. Sequence 900 illustrated in FIGS. 9A-9C includes the sameuser 702 and mobile device 704 illustrated in sequences 700 and 800. Inthis illustration, however, receiver device 706 may be another mobiledevice in possession of another user 702′ to which user 702 desires tosend an electronic message 902 inputted by user 702 into mobile device704. As seen in FIG. 9A, mobile device 704 can further include WiFielements 704(d) configured to transmit electronic messages over theInternet or a cellular network, for example.

In this illustration, the data table stored in the memory of mobiledevice 704 may associate a predetermined rotation with a first messageformat (e.g., an email format), and may further associate an upwardtranslational motion with a second message format (e.g., an SMS textmessage). As shown in FIG. 9B, if user 702 wishes to send message 902 inthe first message format to user 702′, user 702 can cause mobile device704 to rotate 904 in accordance with the predetermined rotation storedin the memory of mobile device 704. Upon detecting rotation 904,comparing it to the predetermined motions stored in the memory, anddetermining that the calculated confidence value meets (or exceeds) thecorresponding threshold value, the processor of mobile device 704 caninitiate a communication mode associated with the first message format.As seen in FIG. 9B, this can involve mobile device 704 sending message902 as a formatted message 908 in the first message format to receiverdevice 706 of user 702′ via a network 906 (e.g., a WiFi networkconnected to the Internet).

Alternatively, as shown in FIG. 9C, user 702 may instead wish to sendmessage 902 in the second message format. In this illustration, insteadof rotation 904, user 702 can move mobile device 704 in an upwardtranslational motion 910 in accordance with the predetermined upwardmotion stored in the memory of mobile device 704. Upon detecting motion910, comparing it to the predetermined motions stored in the memory, anddetermining that the calculated confidence value meets (or exceeds) thecorresponding threshold value, the processor of mobile device 704 caninitiate a communication mode associated with the second message format.As seen in FIG. 9C, this can involve mobile device 704 sending message902 as a formatted message 912 in the second message format to receiverdevice 706 of user 702′ via network 906.

In some embodiments, in a further effort to avoid false positives, theuser may be required to open an application on their mobile devicebefore initiating a predetermined motion of the mobile device. Forexample, a payment application or other suitable application can beopened by way of one or more buttons on the mobile device, touch input(e.g., a selection or specified gesture) provided by the user on a touchscreen of the mobile device, and/or one or more predetermined motions ofthe mobile device. Further, in some embodiments, data other than thatreceived at location determination circuitry of the mobile device can beused to confirm a location of the mobile device. For example, in someembodiments, a merchant may provide a data beacon (e.g., in a Bluetoothformat) by way of a transmitter near the merchant's front entrance, nearthe check-out area at the POS terminal, etc. Such a beacon may bedetected by the mobile device, and may confirm that the mobile device islocated at a merchant.

III. Exemplary Computer Apparatus

The various participants and elements described herein with reference toFIGS. 1-9C may operate one or more computer apparatus to facilitate thefunctions described herein. Any of the elements in FIGS. 1-9C may useany suitable number of subsystems to facilitate the functions describedherein.

Examples of such subsystems or components are shown in FIG. 10 whichillustrates exemplary computer apparatus 1000. The subsystems shown inFIG. 10 are interconnected via a system bus 1002. Additional subsystemssuch as a printer 1010, keyboard 1016, fixed disk 1018 (or other memorycomprising computer readable media), monitor 1022, which is coupled to adisplay adapter 1012, and others are shown. Peripherals and input/output(I/O) devices, which couple to I/O controller 1004 (which can be aprocessor or other suitable controller), can be connected to thecomputer system by any number of means known in the art, such as aserial port 1014. For instance, serial port 1014 or an externalinterface 1020 can be used to connect computer apparatus 1000 to a widearea network such as the Internet, a mouse input device, or a scanner.The interconnection via system bus 1002 allows a central processor 1008to communicate with each subsystem and to control the execution ofinstructions from a system memory 1006 or fixed disk 1018, as well asthe exchange of information between subsystems. System memory 1006and/or fixed disk 1018 may embody a computer readable medium (e.g., anon-transitory computer readable medium).

Further, while the present invention has been described using aparticular combination of hardware and software in the form of controllogic and programming code and instructions, it should be recognizedthat other combinations of hardware and software are also within thescope of the present invention. The present invention may be implementedonly in hardware, or only in software, or using combinations thereof.

Any of the software components or functions described in thisapplication, may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C++ or Perl using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructions,or commands on a computer readable medium, such as a random accessmemory (RAM), a read only memory (ROM), a magnetic medium such as ahard-drive or a floppy disk, or an optical medium such as a CD-ROM. Anysuch computer readable medium may reside on or within a singlecomputational apparatus, and may be present on or within differentcomputational apparatuses within a system or network.

The above description is illustrative and is not restrictive. Manyvariations of the invention will become apparent to those skilled in theart upon review of the disclosure. The scope of the invention should,therefore, be determined not with reference to the above description,but instead should be determined with reference to the pending claimsalong with their full scope or equivalents.

One or more features from any embodiment may be combined with one ormore features of any other embodiment without departing from the scopeof the invention.

A recitation of “a”, “an” or “the” is intended to mean “one or more”unless specifically indicated to the contrary.

All patents, patent applications, publications, and descriptionsmentioned above are herein incorporated by reference in their entiretyfor all purposes. None is admitted to be prior art.

What is claimed is:
 1. A mobile device comprising: a motion detectionsensor; a communication interface; and a processor coupled to the motiondetection sensor and the communication interface, the processorconfigured to: receive a signal from the motion detection sensor, thesignal identifying a motion of the mobile device detected by the motiondetection sensor; compare the detected motion of the mobile device to aplurality of predetermined motions, each of the plurality ofpredetermined motions being associated with a different communicationmode of the mobile device; identify a communication mode associated withthe detected motion of the mobile device based at least on part on thecomparison, the identified communication mode corresponding to acommunication protocol; generate a data message in accordance with thecommunication protocol; and provide the data message to a receiverdevice via the communication interface.
 2. The mobile device of claim 1,wherein providing the data message to the receiver device compriseswirelessly transmitting the data message to the receiver device.
 3. Themobile device of claim 1, wherein the communication interface comprisesa display screen, and wherein providing the data message to the receiverdevice comprises displaying the data message on the display screen. 4.The mobile device of claim 1, wherein comparing the detected motion ofthe mobile device to the plurality of predetermined motions comprises:calculating a confidence value that the detected motion of the mobiledevice corresponds to one of the plurality of predetermined motions; andcomparing the calculated confidence value to a threshold confidencevalue.
 5. The mobile device of claim 4, wherein identifying thecommunication mode associated with the detected motion of the mobiledevice comprises determining that the calculated confidence value isequal to or greater than the threshold confidence value.
 6. The mobiledevice of claim 1, further comprising location determination circuitrycoupled to the processor, the processor being further configured to:receive a signal from the location determination circuitry, the signalidentifying a location of the mobile device determined by the locationdetermination circuitry; and identify the communication mode associatedwith the detected motion of the mobile device based in part on thedetermined location of the mobile device and in part on the comparison.7. The mobile device of claim 1, wherein the motion detection sensorcomprises one or more of an accelerometer, a gyroscope, a compass, andan altimeter.
 8. The mobile device of claim 1, wherein the detectedmotion of the mobile device comprises a rotation of the mobile device.9. The mobile device of claim 1, wherein the detected motion of themobile device comprises a translational motion of the mobile device. 10.The mobile device of claim 1, further comprising a memory coupled to theprocessor, the memory storing the plurality of predetermined motionsassociated with the different communication modes of the mobile device.11. A method for motion-based selection of a communication mode, themethod comprising: detecting, by a mobile device, a motion of the mobiledevice; comparing, by the mobile device, the detected motion of themobile device to a plurality of predetermined motions, each of theplurality of predetermined motions being associated with a differentcommunication mode of the mobile device; identifying, by the mobiledevice, a communication mode associated with the detected motion of themobile device based at least on part on the comparison, the identifiedcommunication mode corresponding to a communication protocol;generating, by the mobile device, a data message in accordance with thecommunication protocol; and providing, by the mobile device, the datamessage to a receiver device.
 12. The method of claim 11, whereinproviding the data message to the receiver device comprises: wirelesslytransmitting, by the mobile device, the data message to the receiverdevice.
 13. The method of claim 11, wherein providing the data messageto the receiver device comprises: displaying, by the mobile device, thedata message on a display screen of the mobile device.
 14. The method ofclaim 11, wherein comparing the detected motion of the mobile device tothe plurality of predetermined motions comprises: calculating, by themobile device, a confidence value that the detected motion of the mobiledevice corresponds to one of the plurality of predetermined motions; andcomparing, by the mobile device, the calculated confidence value to athreshold confidence value.
 15. The method of claim 14, whereinidentifying the communication mode associated with the detected motionof the mobile device comprises: determining, by the mobile device, thatthe calculated confidence value is equal to or greater than thethreshold confidence value.
 16. The method of claim 11, furthercomprising: determining, by the mobile device, a location of the mobiledevice; and identifying, by the mobile device, the communication modeassociated with the detected motion of the mobile device based in parton the determined location of the mobile device and in part on thecomparison.
 17. The method of claim 11, wherein the motion of the mobiledevice is detected by a motion detection sensor of the mobile device,the motion detection sensor comprising one or more of an accelerometer,a gyroscope, a compass, and an altimeter.
 18. The method of claim 11,wherein the detected motion of the mobile device comprises a rotation ofthe mobile device.
 19. The method of claim 11, wherein the detectedmotion of the mobile device comprises a translational motion of themobile device.
 20. The method of claim 11, wherein the plurality ofpredetermined motions associated with the different communication modesof the mobile device are stored in a memory of the mobile device.